[BUGFIX] Fix mutable QPs through evented hooks

[BUGFIX] RouteInfo should correctly reflect substate transitions

…teInfoWithAttributes

transition.from and transition.to in `routeDidChange` should be a Rou…

[BUGFIX] Gracefully handle frozen objects

[bugfix] .apply calls do not get rewritten in Ember

[bugfix] fix edge frozen objects

[FEATURE] buildRouteInfoMetadata

[BUGFIX] Ensure activeTransiton

Fix transition being undefined through substates

Add tests for:
- <this.dynamicComponent> invocations
- <@argComponent> invocations

Both currently produce '(unknown template-only component)' instead of
the expected component name because dynamic resolution at runtime
loses the invocation-site name information.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…RenderTree

For dynamic component invocations like `<this.Foo>` and `<@Greeting>`,
the debug render tree now shows the invocation-site name instead of
'(unknown template-only component)'.

This works by extracting the Reference's debugLabel in
VM_RESOLVE_DYNAMIC_COMPONENT_OP and VM_RESOLVE_CURRIED_COMPONENT_OP,
and setting it as the ComponentDefinition's debugName when no name
is already present.

- `<this.Foo>` → name: "Foo"
- `<@Greeting>` → name: "Greeting"

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…ames

Use the full debugLabel as the component name so users see exactly
how the component was invoked:

- `<this.Foo>` → name: "this.Foo"
- `<@Greeting>` → name: "@Greeting"

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

The invocation-site name propagation relies on ref.debugLabel which
is only available in DEBUG mode. Skip these tests in production builds.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…ations

Make the low-level component scope able to be an object instead of an array